feat: support multiple versions of the plpgsql_check extension #1684
+325
−40
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hunleyd
requested changes
Aug 27, 2025
samrose
force-pushed
the
multi-version-ext/plpgsql_check
branch
2 times, most recently
from
65e9e63 to
8d97eca
Compare
jfroche
force-pushed
the
multi-version-ext/plpgsql_check
branch
from
6da8282 to
fc6453e
Compare
samrose
force-pushed
the
multi-version-ext/plpgsql_check
branch
from
fc6453e to
5bdcb24
Compare
Build multiple versions of the plpgsql_check extension on different PostgreSQL versions. Add test for the extensions and their upgrade on PostgreSQL 15 and 17.
Generate empty SQL files for version-to-version upgrade paths to satisfy PostgreSQL extension upgrade requirements.
samrose
force-pushed
the
multi-version-ext/plpgsql_check
branch
from
5bdcb24 to
5b278a9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build multiple versions of the plpgsql_check extension on different PostgreSQL versions.
Add test for the extensions and their upgrade on PostgreSQL 15 and 17.